Phase 0 scaffold: package skeleton, tooling, CI with coverage#39
Merged
Conversation
- pyproject.toml: hatchling + src layout, py>=3.12, pydantic core dep; ruff config copied from the writeitai house style (team-harness/ loopy-loop); pyright deliberately DEVIATES from that template — "standard" mode with no checks disabled (strict-first for a data-integrity system); pytest with asyncio auto + coverage config - src/ultimate_memory: versioned package with py.typed; src/tests: smoke tests - CI (GitHub Actions): uv-based, locked sync, 3.12/3.13 matrix, ruff lint + format check, pyright, pytest with coverage; coverage published via py-cov-action (self-contained: PR comments + badge from a data branch, no external service) - README: CI + coverage badges; banner updated (implementation begun, roadmap phase 0); Makefile dev targets; .gitignore python entries - uv.lock committed: CI runs pinned tool/dep versions; bumps are deliberate Package name "ultimate-memory" is the working title; rename gates public release (questions.md #11a). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
||||||||||||||||||||||||
…ts); codify relax-with-receipts rule Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
First implementation commit (roadmap phase 0): the package skeleton and the full quality gate, so every subsequent PR lands against working checks.
pyproject.toml— hatchling +src/layout, Python ≥3.12, Apache-2.0. Ruff config copied verbatim from the writeitai house style (team-harness/loopy-loop:I,B,A,ERA, single-line imports, 88 cols). Pyright deliberately deviates from that template:standardmode with zero disabled checks (the template runsbasic+ ~20report*=false) — strict-first for a data-integrity system full of enums and adjudication outcomes; loosen only per-line with a reason.--lockedsync (committeduv.lock= pinned tools, no lint drift), 3.12/3.13 matrix, ruff lint + format check, pyright, pytest.py-cov-action/python-coverage-comment-action: PR comments with coverage diffs + a badge served from a data branch in this repo. No external service, no tokens to configure. Badges added to the README (coverage badge lights up after the first post-merge run onmain).src/ultimate_memory(versioned,py.typed) + smoke tests; Makefile dev targets (make check= lint + typecheck + test); README banner updated (implementation begun).All checks green locally: ruff clean, pyright 0 errors in standard mode, 2/2 tests, coverage 66.7% (missed lines = the not-installed fallback branch).
Notes
ultimate-memoryis the working title; the rename gates public release, not development (questions.md #11a). PyPI/npm/Docker collision state is irrelevant until then.checks (3.12),checks (3.13), andCoverage report.🤖 Generated with Claude Code